feat: RFC 9535 compliance with Peggy parser#15
Merged
Conversation
765df85 to
c1ccbc9
Compare
c1ccbc9 to
9120fa3
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR achieves full RFC 9535 compliance for jsonpathly by replacing the ANTLR4 parser with Peggy and implementing all required features.
Key Changes
length(value)- string/array length or object key countcount(nodelist)- count of nodes in nodelistmatch(string, pattern)- full string I-Regexp matchsearch(string, pattern)- substring I-Regexp matchvalue(nodelist)- extract single value from nodelistBug Fixes
Breaking Changes
$["key"]to$['key'](RFC 9535 normalized format)Closes
Test plan